Migrate Index Management to the new ES JS client #105863

cjcenizal · 2021-07-15T22:56:17Z

This PR migrates Index Management to the new ES JS client. Other changes:

CCR, ILM, and Rollup index enrichers were also migrated.
Migrated API integration and unit tests.
Migrated route error handling to modern handleEsError pattern.

Note that I added numerous @ts-expect-error comments to silence TS complaints. I expect that we'll address these in subsequent PRs. I also discovered UX flaws and test coverage gaps, which I noted under my "Notes" section below. We'll also address these in subsequent PRs. All of these are noted under the "Follow-up items" section below.

Things to test

I've made suggestions about how to break up this testing work, but feel free to disregard this if you'd prefer to test in a different way.

(@sabarasaba) Test the CCR, ILM, and Rollup enrichers by following the testing steps in each of those plugins' READMEs.
(@sabarasaba) Try out the different index-level actions in Index Management: freeze, unfreeze, open, close, and so on. Perform these actions on both individual indices and on bulk indices. See "Special test cases" below for further testing.
(@sabarasaba) Follow the instructions in the Index Management README to create a data stream. Verify that it appears in the data streams tab and that toggling "Include stats" surfaces additional stats in the table. See "Special test cases" below for further testing.
(@alisonelizabeth) Go through the indices, index templates, and component templates tabs and verify that the basic CRUD operations work. See "Special test cases" below for further testing.
(@alisonelizabeth) Examine each tab in the index details flyout and verify there aren't any errors. Edit an index's settings.

Special test cases

Indices with special characters

We added support for special characters in index names like %{[@metadata][beat]}-%{[@metadata][version]}-2020.08.23 with #76584. You can create this index in Console like this:

PUT %25%7B%5B%40metadata%5D%5Bbeat%5D%7D-%25%7B%5B%40metadata%5D%5Bversion%5D%7D-2020.08.23

Test that all actions can be performed on this index.

Data streams with special characters

Similar to the above, data streams also support special characters in their names and we need to test that we can fetch them, both with and without stats, and also delete them. You can create this kind of data stream in Console like this:

# Configure template for creating a data stream
PUT _index_template/special_ds
{
  "index_patterns": ["%{[@metadata][beat]}-%{[@metadata][version]}-2020.08.23"],
  "data_stream": {}
}

# Add a document to the data stream
POST %25%7B%5B%40metadata%5D%5Bbeat%5D%7D-%25%7B%5B%40metadata%5D%5Bversion%5D%7D-2020.08.23/_doc
{
  "@timestamp": "2020-01-27"
}

Legacy index templates

Follow the Index Management README instructions to get legacy index templates to appear in the UI.

Follow-up items

I'll create individual issues to track these items.

Add more detailed notes on testing gaps to Index Management API integration test coverage #106168
Convert API integration tests to TS Convert Index Management API integration tests to TS #107483
Reorganize API integration tests to make them easier to traverse and maintain Reorganize Index Management API integration tests #107482
Remove @ts-expect-error comments where possible and file issues for missing/incorrect types in elasticsearch-specification
Rename component template route handler files to follow the same pattern as the other files Index Management ES JS client migration followup #107463
Consolidate the way missing Index Management privileges are handled by the UI Consolidate Index Management missing privileges UX #107484
Surface missing error details in the UI when you try to delete a missing component template Surface missing error details in the Index Management UI #107485

Notes

To-do

Route audit

Component templates

Route	Notes	API test / error	Local test
Create component template	Collision check	✅ 🚫	✅
Delete component template	Split on comma	✅ ✅	✅
Get all component templates		✅ 🚫	✅
Get one component template		✅ 🚫	✅
Component template privileges	Test is sparse, made up for by unit tests	✅ 🚫	✅
Update component template		✅ ✅	✅

Data streams

Route	Notes	API test / error	Local test
Delete data stream(s)		🔧 🚫	✅
Get all data streams	Include stats option, encodeURIComponent	✅ 🚫	✅
Get one data stream	Include stats option, encodeURIComponent	🔧 🚫	✅

Indices

Notes: Tested listing, freezing, and unfreezing with indices with special characters, per #76584.

Route	Notes	API test / error	Local test
Clear cache	Bulk	✅ 🚫	✅
Close	Bulk	🔧 🚫	✅
Delete	Bulk	🔧 🚫	✅
Flush	Bulk	🔧 🚫	✅
Force merge	Bulk, `maxNumSegments` option	🔧 🚫	✅
Freeze	Bulk	🔧 🚫	✅
List	Bulk, enrich	✅ 🚫	✅
Open	Bulk	🔧 🚫	✅
Refresh	Bulk	🔧 🚫	✅
Reload	Bulk, enrich	✅ 🚫	✅
Unfreeze	Bulk	🔧 🚫	✅

Mapping

Notes: Tested with special characters, per #76584.

Route	Notes	API test / error	Local test
Get mapping		✅ 🚫	✅

Settings

Notes: Tested with special characters, per #76584.

Route	Notes	API test / error	Local test
Load settings		✅ 🚫	✅
Update settings		✅ 🚫	✅

Stats

Notes: Tested with special characters, per #76584.

Route	Notes	API test / error	Local test
Get stats		✅ 🚫	✅

Index templates

Route	Notes	API test / error	Local test
Create index template	Collision check, legacy option	🔧 ✅	✅
Delete index template	Bulk, legacy option	🔧 🚫	✅
Get all index templates	Cloud-managed, includes legacy	🔧 🚫	✅
Get one index template	Cloud-managed, legacy option (has no error message)	🔧 🚫	✅
Simulate		🚫 🚫	✅
Update index template	Exist check, legacy option	🔧 ✅	✅

Error-handling

Index Management privileges

When testing with a user with the following privileges, Index Management is accessible, but the Indices and Data Streams tabs report the privileges error.

index_management_user: {
  elasticsearch: {
    cluster: ['monitor', 'manage_index_templates'],
  },
},

Reducing it further shows error for index and component templates too:

index_management_user: {
  elasticsearch: {
    cluster: ['monitor'],
  },
},

Note: Component templates has a specific privileges check for manage_index_templates and renders a custom error message.

Deleting index templates

If you delete an index template that's in use by a data stream, you'll get back lots of error details but they aren't surfaced in the UI. Ideally you should be able to click a button in the error toast to get more info.

{
  "templatesDeleted": [
    "special%"
  ],
  "errors": [
    {
      "name": "special",
      "error": {
        "status": 400,
        "payload": {
          "message": "unable to remove composable templates [special] as they are in use by a data streams [special%]",
          "attributes": {
            "error": {
              "root_cause": [
                {
                  "type": "illegal_argument_exception",
                  "reason": "unable to remove composable templates [special] as they are in use by a data streams [special%]"
                }
              ],
              "type": "illegal_argument_exception",
              "reason": "unable to remove composable templates [special] as they are in use by a data streams [special%]"
            }
          }
        },
        "options": {
          "statusCode": 400,
          "body": {
            "message": "unable to remove composable templates [special] as they are in use by a data streams [special%]",
            "attributes": {
              "error": {
                "root_cause": [
                  {
                    "type": "illegal_argument_exception",
                    "reason": "unable to remove composable templates [special] as they are in use by a data streams [special%]"
                  }
                ],
                "type": "illegal_argument_exception",
                "reason": "unable to remove composable templates [special] as they are in use by a data streams [special%]"
              }
            }
          }
        }
      }
    }
  ]
}

Deleting component templates

Similarly, if you delete component templates that no longer exist, you'll get back lots of error details but they aren't surfaced in the UI. Ideally you should be able to click a button in the error toast to get more info.

{
  "itemsDeleted": [],
  "errors": [
    {
      "name": "trvdfvds",
      "error": {
        "status": 404,
        "payload": {
          "message": "trvdfvds",
          "attributes": {
            "error": {
              "root_cause": [
                {
                  "type": "resource_not_found_exception",
                  "reason": "trvdfvds"
                }
              ],
              "type": "resource_not_found_exception",
              "reason": "trvdfvds"
            }
          }
        },
        "options": {
          "statusCode": 404,
          "body": {
            "message": "trvdfvds",
            "attributes": {
              "error": {
                "root_cause": [
                  {
                    "type": "resource_not_found_exception",
                    "reason": "trvdfvds"
                  }
                ],
                "type": "resource_not_found_exception",
                "reason": "trvdfvds"
              }
            }
          }
        }
      }
    },
    {
      "name": "test",
      "error": {
        "status": 404,
        "payload": {
          "message": "test",
          "attributes": {
            "error": {
              "root_cause": [
                {
                  "type": "resource_not_found_exception",
                  "reason": "test"
                }
              ],
              "type": "resource_not_found_exception",
              "reason": "test"
            }
          }
        },
        "options": {
          "statusCode": 404,
          "body": {
            "message": "test",
            "attributes": {
              "error": {
                "root_cause": [
                  {
                    "type": "resource_not_found_exception",
                    "reason": "test"
                  }
                ],
                "type": "resource_not_found_exception",
                "reason": "test"
              }
            }
          }
        }
      }
    }
  ]
}

* Destructure index API request bodies consistently. * Update tests. * Migrate enrichers.

- Migrate create and update index template routes to handleEsError.

* Fix simulate endpoint and move elasticsearch/issues/59152 workaround to server. * Remove commented-out code and unnecessary types from fetch_indices. * Convert to IScopedClusterClient in a few places. * Delete wrapEsError helpers. * Remove unnecessary calls to encodeURIComponent on the server.

elasticmachine · 2021-07-20T18:17:08Z

Pinging @elastic/kibana-stack-management (Team:Stack Management)

cjcenizal · 2021-07-20T20:06:27Z

x-pack/plugins/index_management/server/routes/api/templates/register_update_route.ts

+        } = template;
+
+        // Verify the template exists (ES will throw 404 if not)
+        const { body: templateExists } = await doesTemplateExist({ name, client, isLegacy });


Moved the logic inside the try/catch so we could catch any ES errors from the helpers.

cjcenizal · 2021-07-20T20:08:37Z

x-pack/test/api_integration/apis/management/index_management/component_templates.ts

@@ -281,8 +281,19 @@ export default function ({ getService }: FtrProviderContext) {
        expect(body).to.eql({
          statusCode: 404,
          error: 'Not Found',
-          message:
-            '[resource_not_found_exception] component template matching [component_does_not_exist] not found',
+          message: 'component template matching [component_does_not_exist] not found',


The errors we get now are more consistent with what we get from ES, which I think is a good thing for making our error-handling UX more consistent (see #84801).

cjcenizal · 2021-07-20T20:09:46Z

x-pack/plugins/index_management/server/lib/get_managed_templates.ts

-      includeDefaults: true,
+    const {
+      body: { persistent, transient, defaults },
+    } = await client.asCurrentUser.cluster.getSettings({


I didn't test this -- could someone look into setting these settings manually and verifying there are no errors?

Implemented via #43901.

Looks like it is working as expected for both composable and legacy index templates.

cjcenizal · 2021-07-20T20:10:44Z

x-pack/test/api_integration/apis/management/index_management/templates.js

@@ -193,8 +193,8 @@ export default function ({ getService }) {
      });

      it('should parse the ES error and return the cause', async () => {
-        const templateName = `template-${getRandomString()}`;
-        const payload = getTemplatePayload(templateName, [getRandomString()]);
+        const templateName = `template-create-parse-es-error}`;


I found these hardcoded strings very handy when I was debugging these tests by looking at the functional test runner logs.

alisonelizabeth

Nice work on this @cjcenizal! Great to see all of our apps migrated 🎉 . I left a few comments/questions in the code. Let me know what you think.

(@alisonelizabeth) Go through the indices, index templates, and component templates tabs and verify that the basic CRUD operations work. See "Special test cases" below for further testing.
(@alisonelizabeth) Examine each tab in the index details flyout and verify there aren't any errors. Edit an index's settings.

👍 Tested these items and everything worked as expected. I'll defer to @sabarasaba on the other items.

Also, now that we've migrated all of our apps, can we safely delete the is_es_error util from es_ui_shared? (Perhaps as a follow-up item.)

alisonelizabeth · 2021-07-26T15:58:45Z

x-pack/plugins/index_management/README.md

+
+## Index templates tab
+
+### Quick steps for texting


Suggested change

### Quick steps for texting

### Quick steps for testing

Can we also add a section on how to test cloud-managed templates?

See instructions on #43901.

Great catch, done.

alisonelizabeth · 2021-07-26T16:04:15Z

x-pack/plugins/index_management/server/lib/fetch_indices.ts

        documents: hit['docs.count'],
        size: hit['store.size'],
        isFrozen: hit.sth === 'true', // sth value coming back as a string from ES
        aliases: aliases.length ? aliases : 'none',
+        // @ts-expect-error Property 'index' does not exist on type 'IndicesIndexSettings | IndicesIndexStatePrefixedSettings'.


I believe any ts errors due to lack of coverage/incorrect types in the es js client should be commented as // @ts-expect-error @elastic/elasticsearch ....

I'm not sure it's incorrect typing - according to @elastic/elasticsearch typings it should be refactored to hidden: index.settings.hidden

I just tested this and verified that the original path (index.settings.index.hidden) is correct. I've updated all the annotations to be // @ts-expect-error @elastic/elasticsearch.

@cjcenizal if you are sure there is a problem you should report it to the client team.

Thanks. This is listed as a follow-up item in the PR description.

alisonelizabeth · 2021-07-26T16:11:18Z

x-pack/plugins/index_management/server/lib/get_managed_templates.ts

-      includeDefaults: true,
+    const {
+      body: { persistent, transient, defaults },
+    } = await client.asCurrentUser.cluster.getSettings({


Implemented via #43901.

Looks like it is working as expected for both composable and legacy index templates.

alisonelizabeth · 2021-07-26T16:19:11Z

x-pack/plugins/index_management/server/routes/api/data_streams/register_get_route.ts

-const getDataStreamsStats = (client: ElasticsearchClient, name = '*') => {
-  return client.transport.request({
+const getDataStreamsStats = (client: IScopedClusterClient, name = '*') => {
+  return client.asCurrentUser.transport.request({


Does this comment apply here as well, or can we use client.indices.dataStreamsStats?

// TODO update when elasticsearch client has update requestParams...

Good catch, fixed.

alisonelizabeth · 2021-07-26T16:20:21Z

x-pack/plugins/index_management/server/routes/api/data_streams/register_get_route.ts

@@ -68,9 +68,9 @@ const enhanceDataStreams = ({
  });
 };

-const getDataStreams = (client: ElasticsearchClient, name = '*') => {
+const getDataStreams = (client: IScopedClusterClient, name = '*') => {
  // TODO update when elasticsearch client has update requestParams for 'indices.getDataStream'


Do we need to open an issue for this?

The method is already available in the new client https://github.com/elastic/kibana/blob/b84b51cc02e78ba76c0de289aa379b0f7144263d/x-pack/plugins/fleet/server/services/epm/elasticsearch/template/template.ts#L498

Also fixed.

alisonelizabeth · 2021-07-26T16:29:50Z

x-pack/plugins/index_management/server/routes/api/templates/register_create_route.ts

+
+        return response.ok({ body: responseBody });
+      } catch (error) {
+        return handleEsError({ error, response });


Does the handleEsError util provide the same functionality as before? I see previously it looks like we were parsing the error and passing it to body.attributes.

const error = lib.parseEsError(e.response);

I just tested this. Looks like errors are surfaced correctly by the UI:

alisonelizabeth · 2021-07-26T16:31:08Z

x-pack/plugins/index_management/server/routes/api/templates/register_get_routes.ts

+
+        return response.ok({ body });
+      } catch (error) {
+        if (isEsError(error)) {


Can we use the handleEsError util here instead?

I think this might be the only case where we're still using isEsError, so if we're able to remove it here, we should also be able to remove it from shared_imports and the api routes setup.

Great idea! Done.

alisonelizabeth · 2021-07-26T16:32:52Z

x-pack/plugins/index_management/server/routes/api/templates/register_simulate_route.ts

-        throw e;
+        return response.ok({ body: templatePreview });
+      } catch (error) {
+        return handleEsError({ error, response });


Same question here about the previous behavior of parsing the ES error.

I tested this and it shows up in the UI. We should probably add error-handling logic so it's rendered as an error.

sabarasaba

Nice one @cjcenizal! I tested all the following items items and I didn't find any regressions:

(@sabarasaba) Test the CCR, ILM, and Rollup enrichers by following the testing steps in each of those plugins' READMEs.
(@sabarasaba) Try out the different index-level actions in Index Management: freeze, unfreeze, open, close, and so on. Perform these actions on both individual indices and on bulk indices. See "Special test cases" below for further testing.
(@sabarasaba) Follow the instructions in the Index Management README to create a data stream. Verify that it appears in the data streams tab and that toggling "Include stats" surfaces additional stats in the table. See "Special test cases" below for further testing.
+special cases

* With steps for testing Cloud-managed index templates * With steps for testing indices and data streams that contain special characters

* Remove unused isEsError and parseEsError dependencies.

cjcenizal · 2021-07-31T00:16:57Z

Thanks for the reviews @sabarasaba and @alisonelizabeth! Alison, I believe I've addressed your comments. Could you please take another look?

alisonelizabeth

Thanks for addressing my feedback @cjcenizal! Did not retest, but reviewed the changes and everything LGTM.

sabarasaba · 2021-08-02T14:52:22Z

Thanks @cjcenizal! Latest changes lgtm also 🥳

…ic#105863) * Destructure index API request bodies consistently. * Remove unnecessary calls to encodeURIComponent on the server. * Migrate routes to handleEsError. Delete wrapEsError helpers. Remove unused isEsError and parseEsError dependencies. Remove isEsError from es_ui_shared. * Update tests and migrate API integration tests. * Clarify test details in CCR README. Update Index Management README with steps for testing Cloud-managed index templates and steps for testing indices and data streams that contain special characters. # Conflicts: # x-pack/plugins/index_management/server/routes/api/templates/register_create_route.ts # x-pack/plugins/index_management/server/routes/api/templates/register_get_routes.ts # x-pack/plugins/index_management/server/routes/api/templates/register_update_route.ts

kibanamachine · 2021-08-02T21:02:24Z

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`indexManagement`	1.3MB	1.3MB	-56.0B

Unknown metric groups

API count

id	before	after	diff
`esUiShared`	92	90	-2

API count missing comments

id	before	after	diff
`esUiShared`	90	88	-2

References to deprecated APIs

id	before	after	diff
`crossClusterReplication`	2	0	-2
`indexLifecycleManagement`	2	0	-2
`indexManagement`	12	0	-12
total			-16

History

💚 Build #142324 succeeded d78dacd
💔 Build #142121 failed 0ed2d64
💔 Build #142112 failed 0b4f32c65e4d64654c3942617b9b6417215059eb
💔 Build #142108 failed 88a2e09
💚 Build #139865 succeeded b84b51cc02e78ba76c0de289aa379b0f7144263d

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

…105863) (#107431) * Migrate Index Management and enrichers to the new ES JS client (#105863) * Destructure index API request bodies consistently. * Remove unnecessary calls to encodeURIComponent on the server. * Migrate routes to handleEsError. Delete wrapEsError helpers. Remove unused isEsError and parseEsError dependencies. Remove isEsError from es_ui_shared. * Update tests and migrate API integration tests. * Clarify test details in CCR README. Update Index Management README with steps for testing Cloud-managed index templates and steps for testing indices and data streams that contain special characters. # Conflicts: # x-pack/plugins/index_management/server/routes/api/templates/register_create_route.ts # x-pack/plugins/index_management/server/routes/api/templates/register_get_routes.ts # x-pack/plugins/index_management/server/routes/api/templates/register_update_route.ts * Fix include_type_name type.

…ic#105863) * Destructure index API request bodies consistently. * Remove unnecessary calls to encodeURIComponent on the server. * Migrate routes to handleEsError. Delete wrapEsError helpers. Remove unused isEsError and parseEsError dependencies. Remove isEsError from es_ui_shared. * Update tests and migrate API integration tests. * Clarify test details in CCR README. Update Index Management README with steps for testing Cloud-managed index templates and steps for testing indices and data streams that contain special characters.

cjcenizal mentioned this pull request Jul 15, 2021

Stack Management elasticsearch-js client migration #73973

Closed

17 tasks

cjcenizal added chore Feature:Index Management Index and index templates UI v7.15.0 v8.0.0 labels Jul 15, 2021

cjcenizal force-pushed the index-management/migrate-legacy-es-js-client branch 3 times, most recently from 2138084 to c2d901f Compare July 19, 2021 18:57

cjcenizal mentioned this pull request Jul 19, 2021

Index Management API integration test coverage #106168

Closed

cjcenizal force-pushed the index-management/migrate-legacy-es-js-client branch 2 times, most recently from 4db07da to cb25a9b Compare July 19, 2021 22:55

cjcenizal mentioned this pull request Jul 20, 2021

Calling "simulateIndexTemplate" without a "name" parameter causes client to throw a 500 error elastic/elasticsearch-specification#496

Closed

cjcenizal added the blocked label Jul 20, 2021

cjcenizal force-pushed the index-management/migrate-legacy-es-js-client branch from 42424de to 0d53fc5 Compare July 20, 2021 14:57

cjcenizal changed the title ~~Migrate Index Management to the new ES JS client~~ [skip-ci] Migrate Index Management to the new ES JS client Jul 20, 2021

cjcenizal added 5 commits July 20, 2021 10:54

Migrate Index Management APIs to new ES JS client.

dbedd4a

* Destructure index API request bodies consistently. * Update tests. * Migrate enrichers.

Migrate API integration tests.

a7c8700

- Migrate create and update index template routes to handleEsError.

Migrate remaining routes to handleEsError.

9aba111

Fix or ignore TS errors.

fead8c1

cjcenizal changed the title ~~[skip-ci] Migrate Index Management to the new ES JS client~~ Migrate Index Management to the new ES JS client Jul 20, 2021

cjcenizal added the Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more label Jul 20, 2021

cjcenizal marked this pull request as ready for review July 20, 2021 18:17

cjcenizal requested a review from a team as a code owner July 20, 2021 18:17

cjcenizal force-pushed the index-management/migrate-legacy-es-js-client branch from 0d53fc5 to fead8c1 Compare July 20, 2021 18:17

cjcenizal added release_note:skip Skip the PR/issue when compiling release notes and removed blocked labels Jul 20, 2021

cjcenizal requested review from sabarasaba and alisonelizabeth July 20, 2021 19:43

cjcenizal commented Jul 20, 2021

View reviewed changes

elastic deleted a comment from kibanamachine Jul 20, 2021

cjcenizal mentioned this pull request Jul 20, 2021

[Meta] Switch to the new Elasticsearch client #83910

Closed

74 tasks

alisonelizabeth reviewed Jul 26, 2021

View reviewed changes

Merge branch 'master' into index-management/migrate-legacy-es-js-client

a3b97c0

sabarasaba approved these changes Jul 30, 2021

View reviewed changes

cjcenizal added 6 commits July 30, 2021 11:18

Update Index Management README:

83ce079

* With steps for testing Cloud-managed index templates * With steps for testing indices and data streams that contain special characters

Convert data stream API helpers to use dedicated ES APIs.

a1b4b20

Convert last isEsError remnant to handleEsError.

39bb134

* Remove unused isEsError and parseEsError dependencies.

Remove isEsError from es_ui_shared.

e0056d3

Add @elastic/elasticsearch to @ts-expect-error annotations.

2651a31

Merge branch 'master' into index-management/migrate-legacy-es-js-client

88a2e09

cjcenizal force-pushed the index-management/migrate-legacy-es-js-client branch from b84b51c to 88a2e09 Compare July 31, 2021 00:11

alisonelizabeth approved these changes Jul 31, 2021

View reviewed changes

Rebuild docs.

0ed2d64

cjcenizal force-pushed the index-management/migrate-legacy-es-js-client branch from 0b4f32c to 0ed2d64 Compare July 31, 2021 14:30

Merge branch 'master' into index-management/migrate-legacy-es-js-client

d78dacd

cjcenizal merged commit 3491f05 into elastic:master Aug 2, 2021

cjcenizal deleted the index-management/migrate-legacy-es-js-client branch August 2, 2021 17:20

cjcenizal mentioned this pull request Aug 2, 2021

[7.x] Migrate Index Management and enrichers to the new ES JS client (#105863) #107431

Merged

cjcenizal mentioned this pull request Aug 2, 2021

Index Management ES JS client migration followup #107463

Merged

Migrate Index Management to the new ES JS client #105863

Migrate Index Management to the new ES JS client #105863

Conversation

cjcenizal commented Jul 15, 2021 • edited Loading

Things to test

Special test cases

Indices with special characters

Data streams with special characters

Legacy index templates

Follow-up items

To-do

Route audit

Component templates

Data streams

Indices

Mapping

Settings

Stats

Index templates

Error-handling

Index Management privileges

Deleting index templates

Deleting component templates

elasticmachine commented Jul 20, 2021

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

alisonelizabeth left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

sabarasaba left a comment

Choose a reason for hiding this comment

cjcenizal commented Jul 31, 2021

alisonelizabeth left a comment

Choose a reason for hiding this comment

sabarasaba commented Aug 2, 2021

kibanamachine commented Aug 2, 2021

💚 Build Succeeded

Metrics [docs]

Async chunks

API count

API count missing comments

References to deprecated APIs

History

cjcenizal commented Jul 15, 2021 •

edited

Loading